Please indicate how this would fill our criteria for versioned formulas (https://docs.brew.sh/Versions) and why we might want to ship an older version?

Thanks for taking a look at this pull request.

Redis 7.0 introduces a number of potentially breaking changes, as documented in the release notes. For example, the response structure of an important command for using Redis in clustered mode has changed and hence is not currently compatible with certain clients, such as go-redis/redis which is imported by 3,796 public modules at time of writing.

Redis 6.2 is the previous major.minor version and still receives maintenance updates as per the Redis release cycle. It is also the latest version supported by Amazon ElastiCache for Redis and Google Cloud Memorystore for Redis at time of writing, so there is a good case aside from the particular breaking change referenced to keep the two previous major.minor versions available in Homebrew so that engineers can run the same version locally as they do remotely.

There are also existing versioned formulae for redis@4.0 and redis@3.2

I've had a read through the list of requirements and believe that this formula meets them, but if there's anything that might have been missed, I'd be happy to provide further details.

Looking at the document, can you add a disable! date: "2023-05-27", because: :deprecated_upstream so that it's disabled when Redis drops support for it.

ping @JamieEdge

Apologies for the delayed response.

Before committing this change, please could I ask how the disable date would be calculated for this formula? My understanding is that Redis 6.2 will receive maintenance updates until the release of Redis 8.0. I was not able to find a provisional release date for this next major release.

https://redis.io/docs/about/releases/#release-schedule suggests a major release every year, and a minor release in 6 months. So support will be:

• now: 7.0, 6.2, 6.0
• 6 months: 7.1, 7.0, 6.2
• 1 year: 8.0, 7.1, 7.0

Thanks, that makes sense. I have applied all suggestions now.

@bayandin has triggered a merge.

Thanks @JamieEdge! Without contributions like yours, it'd be impossible to keep homebrew going with the high standards that users have come to expect from the project. You can feel good knowing that you've made the world a tiny bit better for homebrew users around the world! 👍 🎉